-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to receive datastore by name or by id #37
Allow to receive datastore by name or by id #37
Conversation
bf96c5a
to
e154228
Compare
…_fixed_ip_per_eni Fix collection of secordary fixed ip per eni
cff61a1
to
5763a16
Compare
This PR depends on ManageIQ/manageiq#15101 |
@borod108 this PR depends on ManageIQ/manageiq#15101 but could be review at the meanwhile. |
context "when storage exists" do | ||
let(:storage) { FactoryGirl.create(:storage, :name => storage_name, :id => storage_id) } | ||
|
||
it "searches for a storage by its ID" do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would change the "searcher" to "finds" here and in the next examples because when I read this I thought you will have something like expect(Storage).to receive(:find)
5763a16
to
c00b78e
Compare
Datastores on the same setup may have the same name. In order to add a disk on a specific datastore, it is better to use the datastore id. https://bugzilla.redhat.com/show_bug.cgi?id=1450952 https://bugzilla.redhat.com/show_bug.cgi?id=1427498
c00b78e
to
a9c2c12
Compare
Checked commit masayag@a9c2c12 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
Datastores on the same setup may have the same name. In order to add a
disk on a specific datastore, it is better to use the datastore id.
https://bugzilla.redhat.com/show_bug.cgi?id=1450952
https://bugzilla.redhat.com/show_bug.cgi?id=1427498